Visum provides an interface for importing network and timetable information from General Transit Feed data.
The importer reads the individual General Transit Feed files and creates corresponding network objects in Visum, which represent the PuT supply. The importer uses information from the files and generates the following network objects in Visum:
|
GTFS file |
Mandatory |
Visum data model |
|
agency.txt |
Yes |
Entries are transferred as operators |
|
stops.txt |
Yes |
Entries are transferred as stops, stop areas, and/or stop points. The decision as to which elements are created is based on the attributes Location_type and parent_station. If the Location_type is '1' and the parent_station is empty, a stop is created. If the Location_type is '1' and the parent_station is populated, a stop area is created. If the Location_type is '0' or empty and the parent_station is populated, a new node and a new stop point are created and assigned to the stop area or stop. If the Location_type is '0' or empty and the parent_station is not filled either, a new node and stop point, as well as a stop area and stop are created. Stops with the entries Location_type{3,4} are currently ignored. |
|
routes.txt |
Yes |
The entries are interpreted as a lines. The transport systems are set using the entry route_types. The operator is based on the entry agency_id. The line name corresponds to the attribute route_id. |
|
trips.txt |
Yes |
The entries are interpreted as vehicle journeys. The route_id refers to the line of the vehicle journey. The trip_id becomes the number of the vehicle journey. The service_id corresponds to the valid day. If there is a shape_id, the intermediate points are imported from it. If there is a block_id, depending on the import settings, forced chainings can be created with vehicle journeys with an identical block_id. |
|
stop_times.txt |
Yes |
Line routes / line route items, time profiles / time profile items, as well as the content of the vehicle journeys and vehicle journey sections are created from the entries. The trip_id refers to the vehicle journey. The stop_id refers to the stop point. The profile points are created from arrival_time and departure_time. Permissibilities for board/alight at the profile points are controlled via pickup_type and dropoff_type. A separate line route and time profile is generated for each vehicle journey. These can optionally be aggregated afterwards. |
|
shapes.txt |
No |
The entries contain intervals and time periods for specific journeys in the timetable. From this, copies of the vehicle journeys are created for the specified duration and at the specified intervals. |
If your license does not include the Calendar add-on, you will receive a warning during the import process. You can confirm the warning and continue the import. You can use the result, but all vehicle journeys are marked as daily, regardless of restrictions in the original data.
1. From the File menu, choose Export > General Transit Feed.
2. Make the desired changes.
|
Element |
Description |
|---|---|
|
Import from file |
Navigate to the desired GTFS zip file you want to import. Note Please note that the files must be at one level in the zip file and only files of type *.txt can be imported. |
|
Timetable period section |
Start Start of the validity period End End of the validity period Calendar period Selection of the calendar period under consideration:
Note This option is only available with the Calendar / valid days add-on module.
Note This option is only available with the Calendar / valid days add-on module. Date filter If this option is selected, you can choose a single day from the validity period for the import. The validity period is determined from the files calender.txt and calender_dates.txt. Note The option is not available if Annual calendar is selected under Calendar period. |
|
Import exact route courses section |
If this option is selected, the exact route courses are imported and you can make further settings: Create multiple stop points for stops on different courses If this option is selected, multiple stop points are imported for stops on different route courses. Use the option Maximum distance between course and stop point to create a maximum distance between route course and stop point. Note The optional courses are imported as intermediate points of the links, not as nodes. |
|
Default settings |
Default transfer walk time The input value affects transfer_type 0 and 1 in the transfers.txt file, as no time specification is provided for this in the GTFS specification. For transfer_type 2, a minimum walk time applies, which is specified in the transfers.txt file. The times are transferred to the transfer walk time between stop areas or to walk links between access nodes of the stop areas. Maximum time for passenger trip chain If the GTFS data set contains information on the line block (block_id in the trips.txt file), passenger trip chains are created between successive trip elements with this maximum time gap. |
|
Post-processing section |
Aggregate lines and vehicle journeys If this option is selected, the generated line routes are aggregated automatically in Visum. Determine suggestions for operating periods If the option is selected, Visum uses the imported operating days to determine suggestions for Visum operating periods, which can reduce the number of required operating days. Note Subsequent editing of the data is important if the data is from a system that is based on operating days. |
Video: How To Import General Transit Feed Specification (GTFS) Data
